Data integrity protection in storage volumes

ABSTRACT

A plurality of logical volumes are stored at a plurality of sites. A command to execute an operation on a logical volume is received. A determination is made as to whether a rule associated with the logical volume permits execution of the operation on the logical volume. In response to determining that the rule associated with the logical volume permits execution of the operation on the logical volume, the operation is executed on the logical volume.

BACKGROUND

1. Field

The disclosure relates to a method, a system, and a computer program product for data integrity protection in storage volumes.

2. Background

A plurality of sites may be coupled together via one of more networks, wherein each of the plurality of sites may have one or more storage controllers that store data in storage volumes. Some of the sites may be separated by extended distances, such as distances exceeding a thousand kilometer, whereas certain other sites may be relatively proximate to each other. Data replication, i.e., copying of data, may be performed over extended distances between two or more sites for business continuity and disaster recovery. In certain mechanisms, data may be replicated synchronously or asynchronously. Additionally, in certain mechanisms, consistency groups of volumes may be formed at regular intervals in order to allow recovery of data.

The copy services functions performed in the plurality of sites may include many types of operations. For example, point in time copy operations may make it possible to create copies of entire logical volumes or data, nearly instantaneously. Peer to Peer Remote Copy or PPRC operations may make it possible to replicate a storage volume to another control unit in a remote site, either synchronously or asynchronously. In certain computing environments a plurality of storage volumes may be simultaneously copied from a primary site to a recovery site, while maintaining point in time consistency across the plurality of storage volumes.

SUMMARY OF THE PREFERRED EMBODIMENTS

Provided are a method, a system, and a computer program product in which a plurality of logical volumes are stored at a plurality of sites. A command to execute an operation on a logical volume is received. A determination is made as to whether a rule associated with the logical volume permits execution of the operation on the logical volume. In response to determining that the rule associated with the logical volume permits execution of the operation on the logical volume, the operation is executed on the logical volume.

In additional embodiments, in response to determining that the rule associated with the logical volume does not permit execution of the operation on the logical volume, the execution of the operation on the logical volume is avoided.

In further embodiments, a determination is made as to whether a parameter of the command indicates that the rule associated with the logical volume is to be overridden by the command. In response to determining that the rule associated with the logical volume is to be overridden by the command, the operation on the logical volume is executed.

In yet further embodiments, the rule associated with the logical volume restricts a copy operation to be performed on the logical volume to overwrite the logical volume if the logical volume stores a consistent copy of another logical volume. Additionally, a label associated with the logical volume identifies the logical volume.

In certain embodiments, the logical volume is a first logical volume that is in a consistent copy service relationship with a second logical volume. The command is a withdraw command that requests withdrawal of at least the first or the second logical volume from the consistent copy service relationship. The withdraw command is rejected in response to interpreting rules associated with the first or the second logical volume.

In further embodiments, prior to receiving the command to execute the operation on the logical volume, a volume label for the logical volume is set, and the rule is associated with the volume label.

In certain embodiments, the logical volume is in a copy service relationship with another logical volume.

In additional embodiments, the logical volume is configured to perform migration of data or disaster recovery.

BRIEF DESCRIPTION OF THE DRAWINGS

Referring now to the drawings in which like reference numbers represent corresponding parts throughout:

FIG. 1 illustrates a block diagram of a computing environment that includes a plurality of storage controllers controlling a plurality of logical volumes at a plurality of sites, in accordance with certain embodiments;

FIG. 2 illustrates a block diagram that shows an exemplary copy command, in accordance with certain embodiments;

FIG. 3 illustrates a block diagram that shows a rules data structure associated with a logical volume, in accordance with certain embodiments;

FIG. 4 illustrates a block diagram that shows how a secondary volume is restricted from being used as the target of a subsequent point in time copy operation, in accordance with certain embodiments;

FIG. 5 illustrates a block diagram that shows how a withdraw command is rejected, in accordance with certain embodiments;

FIG. 6 illustrates a flowchart that shows first operations performed in the computing environment, in accordance with certain embodiments;

FIG. 7 illustrates a flowchart that shows second operations performed in the computing environment, in accordance with certain embodiments

FIG. 8 illustrates a block diagram of a computational system that shows certain elements that may be included in the storage controllers of FIG. 1, in accordance with certain embodiments.

DETAILED DESCRIPTION

In the following description, reference is made to the accompanying drawings which form a part hereof and which illustrate several embodiments. It is understood that other embodiments may be utilized and structural and operational changes may be made.

Associating Rules with Storage Volumes

Mechanisms are provided for maintaining data integrity in storage volumes that may have been replicated, i.e., copied, across a plurality of sites. Volume labels and rules are associated with storage volumes to place restrictions on operations that may be performed on the storage volumes. For example, if point in time copy operations have been used to consistently copy a first set of volumes to a second set of volumes, and the second set of volumes are expected to be used for data recovery, then the second set of volumes may be restricted from being overwritten via rules that are associated with the second set of volumes. As a result, erroneous commands that attempt to overwrite the second set of volumes may be rejected. The rules associated with the volumes may also restrict or permit other types of operations. Additionally, labels may be associated with the volumes to indicate the identity of the storage volume and to indicate whether the storage volume has original data, copied data, etc.

Exemplary Embodiments

FIG. 1 illustrates a block diagram of a computing environment 100 that has a plurality of storage controllers 102 a, 102 b, . . . , 102 n that are located in a plurality of sites 104 a. 104 b, . . . , 104 n. The plurality of sites 104 a . . . 104 n may be separated by extended distances, such as distances of over a thousand kilometer, or may be more proximate. For example, two sites may be in the same office complex in a first continent, whereas a third site may be in a second continent. The storage controllers 102 a . . . 102 n may be any suitable computational device including those presently known in the art, such as, a personal computer, a workstation, a server, a mainframe, a hand held computer, a palm top computer, a telephony device, a network appliance, a blade computer, a storage server, a storage controller, etc. In certain embodiments, the storage controllers 102 a . . . 102 n may comprise cloud component parts included in a cloud computing environment.

The plurality of sites 104 a . . . 104 n are coupled via a network, such as the Internet, or via some other type of network, such as a storage area network, a local area network, a wide area network, etc. While a single storage controller has been shown in each site, in alternative embodiments a plurality of storage controllers may be present in each site.

A storage controller may control a plurality of logical volumes, wherein a logical volume is a logical representation of a physical storage volume that is used for storing data. For example, the storage controller 102 a may control the logical volumes 106 a . . . 106 p, the storage controller 102 b may control the logical volumes 108 a . . . 108 q, and the storage controller 102 n may control the logical volumes 110 a . . . 110 r.

In certain embodiments, a label and one or more rules are associated with each logical volume. For example, the label 112 and the one or more rules 114 are associated with the logical volume 106 a. Other labels 116, 120, 124, 128, 132 and rules 118, 122, 126, 130, 134 that are associated with other logical volumes are also shown in FIG. 1. The labels 116, 120, 124, 128, 132 may also be referred to a volume labels or logical volume labels.

The labels 112, 116, 120, 124, 128, 132 may provide information that identifies the logical volume. For example, label 128 associated with logical volume 110 a may indicate that the name of the logical volume 110 a is “C”.

The rules 114, 118, 122, 126, 130, 134 may indicate restrictions associated with selected logical volumes, wherein in certain embodiments the restrictions may indicate operations that may or may not be performed on selected logical volumes. For example, the rules 130 associated with logical volume 110 a may indicate that the logical volume 110 a may not be the target of another point in time copy operation. If the logical volume 110 a already stores data copied via a previous point in time copy operation, then performing another point in time copy operation with the logical volume 110 a as the target volume may overwrite the previously stored data that may have to be used in the future for data restoration. Therefore, the rules 130 may restrict the logical volume 110 a from being overwritten.

Therefore, FIG. 1 illustrates certain embodiments in which labels and rules are associated with logical volumes, to provide constraints on the operations that may be performed on the logical volumes.

FIG. 2 illustrates an exemplary command 200, such as a point in time copy command 200 that may be executed in the computing environment 100. The point in time copy command 200 may have parameters comprising a source logical volume 202, a target logical volume 204, and a logical volume rule override flag 206. The point in time copy command 200 is a command to copy a source target volume to the target logical volume. However, if the logical volume rule override flag 206 is set to a default value of “false”, then when the point in time copy command 200 is executed the rules associated with the source logical volume 202 and the target logical volume 204 are also processed to determine whether the point in time copy command will actually copy the source logical volume 202 to the target logical volume 204. For example, if the rules associated with the target logical volume 204 indicate that the target logical volume 204 cannot be the target of any further point in time copy operations, then the point in time copy command 200 will not execute to overwrite the target logical volume 204.

In certain embodiments, if a user sets the logical volume rule override flag 206 to “true” to indicate that rules associated with logical volumes should be overridden, then the point in time copy command 200 is executed to copy the source logical volume 202 to the target logical volume 204 irrespective of any restrictions placed by rules associated with the source logical volume 202 or the target logical volume 204.

Therefore, FIG. 2 illustrates certain embodiments in which commands on logical volumes are executed in the computing environment 100 by taking account of rules associated with logical volumes, in response to setting a logical volume rule override flag to a default value of “false”. If the logical volume rule override flag is set to “true” then the rules associated with logical volumes do not restrict the operation of the commands executed with the logical volumes as parameters.

FIG. 3 illustrates an exemplary embodiment 300 that shows how the rules associated with a logical volume X 302 are maintained in a logical volume rules data structure 304. In an exemplary logical volume rules data structure 304, for a first type of copy operation 306, and a second type of copy operation 308, it is indicated whether it is possible for the logical volume X 302 to be a source 310 or a target 312 volume. For example, the “not allowed” indication 314 in the logical volume rules data structure 304 may be interpreted to indicate (as shown via reference numeral 316) that the first type of copy operation 306 is not permitted where the target of the first type of copy operation is the logical volume X 302, when the logical volume rule override flag of the first type of copy operation is set to the default value of “false”.

FIG. 4 illustrates an exemplary site 400 that has a primary storage controller 402 and a secondary storage controller 404, wherein a primary volume 406 in the primary storage controller 402 has been consistently copied to the secondary volume 408 in the secondary storage controller 406. In certain embodiments, the label 410 associated with the secondary volume 408 may indicate the identity of the secondary volume, and the rules 412 associated with the secondary volume 408 may indicate that the point in time copy operation that uses the secondary volume 408 as the target is not allowed (shown via reference numeral 414), except in the case of reverse restore operations, or if the point in time copy operation's logical volume rule override flag is not set to the default value of “false”.

Therefore, FIG. 4 illustrates certain embodiments in which point in time copy operations are restricted from using as the target those volumes that already store consistently copied data.

FIG. 5 illustrates an exemplary embodiment 500 in which logical volumes C 502 and D 604 are in a consistent copy relationship. If a withdraw command 506 that requests withdrawal of logical volume C, logical volume D, or both logical volumes C and D, is initiated in the computing environment 100, then the withdraw command 506 is rejected based on at least the rules associated with the logical volumes C 502 and D 504.

Therefore, FIG. 5 illustrates certain embodiments in which withdraw commands cannot be used to break a consistent copy relationship between two logical volumes, unless the logical volume rule override flag in the withdraw commands are set to override the rules and labels associated with the two logical volumes.

FIG. 6 illustrates a first set of exemplary operations that may be performed by one or more storage controllers 102 a . . . 102 n present in the computing environment 100.

Control starts at block 600 in which, a plurality of logical volumes 106 a . . . 106 p, 108 a . . . 108 q, 110 a . . . 110 r are stored at a plurality of sites 104 a . . . 104 n, wherein in certain embodiments volume labels and associated rules may be set corresponding to the plurality of logical volumes 106 a . . . 106 p, 108 a . . . 108 q, 110 a . . . 110 r. A command 200 to execute an operation on a logical volume 302 is received (at block 602). In certain embodiments, the logical volume 302 is in a copy service relationship with another logical volume. In other embodiments, the logical volume 302 is configured for migration of data or disaster recovery or some other operation. A determination is made (at block 604) as to whether a rule 304 associated with the logical volume 302 permits execution of the operation on the logical volume. In response to determining (“Yes” branch from block 604) that the rule associated with the logical volume permits execution of the operation on the logical volume, the operation is executed (at block 606) on the logical volume. Also, in response to determining that the rule associated with logical volume does not permit execution of the operation on the logical volume (“No” branch from block 604), the execution of the operation on the logical volume is avoided (at block 608).

Therefore, FIG. 6 illustrates certain embodiments in which rules associated with a logical volume restrict operations that may be performed on the logical volume.

FIG. 7 illustrates a second set of exemplary operations that may be performed by one or more storage controllers 102 a . . . 102 n present in the computing environment 100.

Control starts at block 700 in which, a plurality of logical volumes 106 a . . . 106 p, 108 a . . . 108 q, 110 a . . . 110 r are stored at a plurality of sites 104 a . . . 104 n. A command 200 to execute an operation on a logical volume 302 is received (at block 702).

A determination is made (at block 704) as to whether a parameter 206 of the command indicates that the rule associated with the logical volume is to be overridden by the command. In response to determining that the rule associated with the logical volume is to be overridden by the command, the operation on the logical volume is executed (at block 706).

Therefore, FIG. 7 illustrates certain embodiments in which a logical volume rule override flag's setting may be used to determine whether or not to override a rule associated with a logical volume.

Certain embodiments may provide a mechanism to set volume labels (volume names and/or labels, etc.) and to associate rules with these volume labels. Mechanisms may be provided for a new query to determine a volume's label and associated characteristics. A verbose option may also provide the current copy services relationships for the volume. A bulk option to not just obtain information for a single specific volume but obtain information for all volumes of a particular label in a subsystem may also be provided. In certain additional embodiments, new bits for enforcing or overriding the associated rules during copy services and disaster recovery may be provided. Furthermore, mechanisms for modifying or clearing the volume label and/or rules may also be provided.

In certain embodiments, the volume label may help a user to understand which volumes are being used and copy relationships may be established accordingly. The volume label itself is of value, but because there are so many possible disaster recovery configurations, the meaning of the label and the allowed behavior are also stored. For example, when the label is created for a volume, a mechanism for associating expected behavior and role in disaster recovery algorithms for the volume type are also created and stored in a rules data structure.

In certain embodiments, rule usage and enforcement are performed once logical volume labels and rules are in place. The rule usage and enforcement may also be performed via alternative embodiments in which logical volume labels and rules associated with the logical volume labels are not set and other mechanisms are used for determining the rules. In certain other embodiments, the logical volume labels and rules may be used for other operations besides rule enforcement.

In certain embodiments, the logical volumes may be labeled prior to any copy services relationship being set. In other embodiments, the logical volume labels and associated rules may be used without any copy services relationship being set. In certain embodiments, the logical volume labels and associated rules may be used for data migration or disaster recovery.

In certain embodiments, the logical volumes of interest need not be in any relationship for the enforcement of rules. In certain other embodiments, the rules may prevent a logical volume from being put into a relationship in the first place. For example, in an exemplary embodiment, an exemplary logical volume 0x1000 may have a logical volume label indicating that logical volume 0x1000 is to be used as a point in time copy operation's target. If an establish command is received to make logical volume 0x1000 into a point in time copy operation's source, in certain embodiments the establish command may be rejected.

Additional Embodiment Details

The described operations may be implemented as a method, apparatus or computer program product using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof. Accordingly, aspects of the embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the embodiments may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied there.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java*, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). * Java is a trademark or registered trademark of Sun Microsystems, Inc.

Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

FIG. 8 illustrates a block diagram that shows certain elements that may be included in a system 800 in accordance with certain embodiments. The system 800 may comprise the storage controllers 102 a . . . 102 n and may include a circuitry 802 that may in certain embodiments include at least a processor 804. The system 800 may also include a memory 806 (e.g., a volatile memory device), and storage 808. The storage 808 may include a non-volatile memory device (e.g., EEPROM, ROM, PROM, RAM, DRAM, SRAM, flash, firmware, programmable logic, etc.), magnetic disk drive, optical disk drive, tape drive, etc. The storage 808 may comprise an internal storage device, an attached storage device and/or a network accessible storage device. The system 800 may include a program logic 810 including code 812 that may be loaded into the memory 806 and executed by the processor 804 or circuitry 802. In certain embodiments, the program logic 810 including code 812 may be stored in the storage 808. In certain other embodiments, the program logic 810 may be implemented in the circuitry 802. Therefore, while FIG. 8 shows the program logic 810 separately from the other elements, the program logic 810 may be implemented in the memory 806 and/or the circuitry 802.

In certain embodiments, the storage controllers 102 a . . . 102 n may comprise cloud component parts included in a cloud computing environment. In the cloud computing environment the systems architecture of the hardware and software components involved in the delivery of cloud computing may involve a plurality of cloud components communicating with each other.

Certain embodiments may be directed to a method for deploying computing instruction by a person or automated processing integrating computer-readable code into a computing system, wherein the code in combination with the computing system is enabled to perform the operations of the described embodiments.

The terms “an embodiment”, “embodiment”, “embodiments”, “the embodiment”, “the embodiments”, “one or more embodiments”, “some embodiments”, and “one embodiment” mean “one or more (but not all) embodiments of the present invention(s)” unless expressly specified otherwise.

The terms “including”, “comprising”, “having” and variations thereof mean “including but not limited to”, unless expressly specified otherwise.

The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expressly specified otherwise.

Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more intermediaries.

A description of an embodiment with several components in communication with each other does not imply that all such components are required. On the contrary a variety of optional components are described to illustrate the wide variety of possible embodiments of the present invention.

Further, although process steps, method steps, algorithms or the like may be described in a sequential order, such processes, methods and algorithms may be configured to work in alternate orders. In other words, any sequence or order of steps that may be described does not necessarily indicate a requirement that the steps be performed in that order. The steps of processes described herein may be performed in any order practical. Further, some steps may be performed simultaneously.

When a single device or article is described herein, it will be readily apparent that more than one device/article (whether or not they cooperate) may be used in place of a single device/article. Similarly, where more than one device or article is described herein (whether or not they cooperate), it will be readily apparent that a single device/article may be used in place of the more than one device or article or a different number of devices/articles may be used instead of the shown number of devices or programs. The functionality and/or the features of a device may be alternatively embodied by one or more other devices which are not explicitly described as having such functionality/features. Thus, other embodiments of the present invention need not include the device itself.

At least certain operations that may have been illustrated in the figures show certain events occurring in a certain order. In alternative embodiments, certain operations may be performed in a different order, modified or removed. Moreover, steps may be added to the above described logic and still conform to the described embodiments. Further, operations described herein may occur sequentially or certain operations may be processed in parallel. Yet further, operations may be performed by a single processing unit or by distributed processing units.

The foregoing description of various embodiments of the invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the invention be limited not by this detailed description, but rather by the claims appended hereto. The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended. 

1. A method, comprising: storing, via one or more processors, a plurality of logical volumes, at a plurality of sites; receiving, a command to execute an operation on a logical volume; determining, whether a rule associated with the logical volume permits execution of the operation on the logical volume; and in response to determining that the rule associated with the logical volume permits execution of the operation on the logical volume, executing the operation on the logical volume.
 2. The method of claim 1, the method further comprising: in response to determining that the rule associated with logical volume does not permit execution of the operation on the logical volume, avoiding executing the operation on the logical volume.
 3. The method of claim 1, the method further comprising: determining whether a parameter of the command indicates that the rule associated with the logical volume is to be overridden by the command; and in response to determining that the rule associated with the logical volume is to be overridden by the command, executing the operation on the logical volume.
 4. The method of claim 1, wherein: the rule associated with the logical volume restricts a copy operation to be performed on the logical volume to overwrite the logical volume if the logical volume stores a consistent copy of another logical volume; and a label associated with the logical volume identifies the logical volume.
 5. The method of claim 1, wherein the logical volume is a first logical volume that is in a consistent copy service relationship with a second logical volume; wherein the command is a withdraw command that requests withdrawal of at least the first or the second logical volume from the consistent copy service relationship; and rejecting the withdraw command, in response to interpreting rules associated with the first or the second logical volume.
 6. The method of claim 1, wherein prior to receiving the command to execute the operation on the logical volume, performing: setting a volume label for the logical volume; and associating the rule with the volume label.
 7. The method of claim 1, wherein the logical volume is in a copy service relationship with another logical volume.
 8. The method of claim 1, wherein the logical volume is configured to perform migration of data or disaster recovery. 9-19. (canceled)
 20. A method for deploying computing infrastructure, comprising integrating computer-readable code into a computational device, wherein the code in combination with the computational device performs operations, the operations comprising: storing, a plurality of logical volumes, at a plurality of sites; receiving, a command to execute an operation on a logical volume; determining, whether a rule associated with the logical volume permits execution of the operation on the logical volume; and in response to determining that the rule associated with the logical volume permits execution of the operation on the logical volume, executing the operation on the logical volume.
 21. The method for deploying computing infrastructure of claim 20, the operations further comprising: in response to determining that the rule associated with logical volume does not permit execution of the operation on the logical volume, avoiding executing the operation on the logical volume.
 22. The method for deploying computing infrastructure of claim 20, wherein prior to receiving the command to execute the operation on the logical volume, performing: setting a volume label for the logical volume; and associating the rule with the volume label. 23-25. (canceled) 